COMMENT ⊗   VALID 00004 PAGES
C REC  PAGE   DESCRIPTION
C00001 00001
C00002 00002	Stanford University Terminal Interface Message Processor
C00006 00003	Upcoming TIP Changes
C00010 00004	∂23-Jul-82  1902	ME  	use of TACs    
C00013 ENDMK
C⊗;
Stanford University Terminal Interface Message Processor


CSD has a Terminal Interface Message Processor (Terminal IMP, or TIP),
which provides hardwired or dialup terminal access to other ARPAnet sites
without going through SU-AI, SU-SCORE, or SUMEX-AIM.  It also provides
access to these machines when their direct dialup lines are saturated.
Our TIP is officially called SU-TIP and nicknamed FELT-TIP (a vestige of
the time it was located near Felt Lake).

To use the TIP you first need to know the telephone number for modems of
the same speed as your terminal (unless it is hardwired to the TIP
locally).  DCA policy prohibits the online dissemination of TIP phone
numbers; contact Len Bosack (Bosack@SU-SCORE).  It's in your own best interest
not to have unauthorized hackers (e.g., high school students using an MIT
site) tying up TIP ports.  In addition, these telephone numbers will be
changed every year or so, and only the authorized TIP users will be
informed of the new numbers.  Remember, the TIP you save may be your own!

Once you've dialed up the TIP, you usually need to give the following
commands to open a connection (i.e., TELNET) to SU-AI:

@R<cr>		[or just "E" on either a 110-300 baud or hardwired port]
@O 11<cr>

When a session is done and you have logged out of SU-AI, give the TIP
command

@C<cr>

To get SAIL Datamedia display service read the directions on "Use of DMs
via TIPs" in DM.ME[UP,DOC](5).  In addition, the entire TIP command
language is documented in the "User's Guide to the Terminal IMP" by BBN,
which is found in TIPUG.BBN[UP,DOC].

Send questions and report problems to Bosack@SU-SCORE, the TIP Liaison.
Upcoming TIP Changes

∂11-May-79  1943	Feinler at SRI-KL (Jake Feinler) 	TIP Login  
Date: 11 May 1979 1934-PDT
From: Feinler at SRI-KL (Jake Feinler)
Subject: TIP Login
To:   [SRI-KL]<NETINFO>LIAISON-5-79:


Subject: TIP login

     At the November 1978 Sponsors' Group meeting ARPA and DCA
launched a project to implement "TIP login".  This means that a 
terminal user will have to identify himself to the TIP before 
any network connection can be opened.  It is being implemented to
control access to the network.

     Presently there is not enough core storage in the TIPs to 
implement the necessary code.  Also, we have recently received a 
number of complaints about insufficient buffer space in the TIPs
to handle new terminals being added.  We are therefore proposing
three changes which will free up needed core.

1.  Once again, we will deactivate "old Telnet".  We believe all
previously identified problems with new Telnet within the TIP
have been resolved.  Also, host servers have had over three 
years to implement new Telnet.

2.  We propose to abolish "remote controlled Telnet echoing"
(RCTE).  This is a set of negotiated Telnet options which 
provide a choice of echoing modes.  It has been on-line in various
stages of completion for three years but is not widely used.
Removal of RCTE would return the largest amount of storage of
the three changes, about 600 (decimal) words.  On the balance, 
the general welfare of the network will be better served by
replacing it with the TIP login code.

3.  Code to support the IBM 2741 will be removed from all TIPs.

     DCA requests comments on these proposals by 15 June, 1979.  
Please be sure you info your sponsoring agency.  Tentatively
1 December 1979 is proposed to remove the old code, with cutover
of TIP login in January 1980.

Maj. Raymond E. Czahor
Chief, Arpanet and Special Network Mgmt. Br.
DCA

-------

∂16-May-79  0413	MALMAN at BBN-TENEXE 	tip login    
Date: 16 May 1979 0715-EDT
From: MALMAN at BBN-TENEXE
Subject: tip login
To:   BPM at SU-AI

Brian,
Basically all hosts will be "forced" to change their code to accept
a coded password from a "network login server" as verification of a user.
The user will then only have to login once (to the "network
login server").

Hosts that are slow in changing their code to accept this will have to have
their users login twice. (once the the "network login server" and once to
the host itself (as usual).

Hope this is clear enough...

joel
-------
∂23-Jul-82  1902	ME  	use of TACs    
Users of the SU-TAC (formerly SU-TIP) please note:

When you open a connection to a host from the TAC (as in the @OPEN
command), you must now specify the host in the form:
	H/I
where I is the destintation IMP and H is the host number on that IMP (0 to
3).  For example, SU-AI is 0/11, SCORE is 3/11, MIT-AI is 2/6, S1-A is 1/95.

(It turns out that if the Host number on the IMP is zero, then the old way
of giving the host number still works.  E.g., 0/11 is equivalent to 11.)

To figure out the H/I number for a particular host, take the host's octal
host number (available from the HOST program).  If the number has three
digits or less, then the two low-order octal digits are the IMP number I
and the third digit is the Host number H (remember to convert the number I
from octal to decimal, since the TAC wants a decimal number for I).  (If
the number has less than 3 digits, then H is 0.)

If the octal host number has more than 3 digits, then the 3 low-order digits are
the Host number H and the 3 high-order digits are the IMP number I (again in
octal, so remember to convert to decimal before giving the number to the TAC).

The HOST command now types out this new form of Host/IMP numbers.